Method and system for storing data

ABSTRACT

A method for defining, storing, retrieving and interpreting data as well as a corresponding database system are described above. The method is universally applicable, enabling storing all types of data and structures of data. The method is based on structure elements being self-contained information carriers, represented by pairs of concept and concept value and associated context information. Using the method, data can be organized in hierarchies of structure elements with arbitrary depth and complexity. In spite of its simplicity, the method can reflect connection, context and meaning, however complex, irrespective of types of data and how complex the relations between data may be. Hence, the method represents a fundamental framework for standardized physical data storage of all types of data.

TECHNICAL FIELD

[0001] The present invention concerns a method for defining, storing, retrieving and interpreting data, as well as a database system, in which data is stored according to the method described.

BACKGROUND OF THE INVENTION

[0002] Electronic data processing requires storing structures of data. In general, such data stored in such structures is called a DATABASE. A number of methods are available for this purpose. Most such methods assume a predefined structure type called RECORD. A record describes an object or an event with a number of ATTRIBUTES connected with it. An attribute is a concept expected to receive contents. According to tradition the attributes are contextually connected with a record type and hence are not self-contained carriers of information. In a database, data is stored according to record definitions. Each record type reflects a LOGICAL FILE to contain objects or events being described according to the record definition. A database is a set of such files, fulfilling a certain purpose. A DATABASE SYSTEM is a set of general methods, preferably implemented with programmed software, with the purpose of defining, maintaining, retrieving, and, to some extent, interpreting data in a database.

[0003] A common feature of most database systems is that they effectively can access data on the computer's SECONDARY DATA STORAGE (e.g. hard disk). The secondary data storage of a computer uses BLOCK-addressing when accessing data, and is suitable for permanent storing of data. To obtain effective use of secondary data storage, the possibilities of modifying the database definitions must be restricted.

[0004] Some structure types are not suitable for traditional database systems. They depend on the computer's PRIMARY DATA STORAGE (e.g. Random Access Memory) to obtain effective access to data. The primary data storage is BYTE-addressed and very fast. However, the primary data storage is not suitable for large databases or permanent data storage. DYNAMIC RECORD TYPES is an example of such data types. A dynamic record type can be defined and redefined without affecting existing programs or data. For this type of structures, access mechanisms and context are normally implemented as part of the application program. To achieve effective access to such data, all data need to be accessed in the primary data storage, whereas the secondary data storage is exclusively used for permanent storing of the data.

[0005] Program products storing large quantities of data need to access data in the secondary data storage. For this reason they are limited to fixed record definitions. Hence, in the process of meeting needs for increased software functionality, record definitions have to be enlarged and associated procedures have to be up-dated or added successively. For this reason standard software tends to get out of proportion. This phenomenon is well illustrated by standard application software for business administration (Business systems). The software flexibility is increased by adding new program modules, each reflecting a new aspect of the business. However flexible the software, the user has to comply with the software properties and limitations. The possibilities of adjusting the software to suit the needs of the user are truly limited. Large portions of the business rules are predefined in the software and can be developed only marginally. Many phenomenons appearing naturally in a certain business are excluded from being described within the the the frame of the software.

[0006] A solid reason for this is that the basis for describing objects, events and the domain of rules is determined by the predefined data structure and the corresponding software. Therefore, a more flexible system for physical storing of data, less dependent on predefined data structures and procedures is desirable.

[0007] Further, the current methods for storing data occupy large memory space, as the storing density normally is very low. This is due to the fact that the record definitions are excessive in comparison with the needs of the user.

[0008] Other problems with the current database systems are long data retrieval times, difficulties with modifications of the database and the interface to it. Further, combining data from different databases is complicated.

OBJECT OF THE INVENTION

[0009] Therefore, the object of this invention is to provide a method for defining and storing data, and data retrieval as well as a corresponding database system, which wholly or partly eliminates the problems in the prior-art methods.

[0010] This object is achieved by the invention as described in the appended claims.

SUMMARY OF THE INVENTION

[0011] The invention concerns a method for defining, storing, retrieving and interpreting data, in which data is represented in self-contained carriers of information, called structure elements, comprising a data element which in turn comprises a concept (CPT) and a concept value (INS), the structure elements being stored in a structure element file. Particularly, the structure elements further are assigned an identification element (SID), enabling unique identification of structure elements, and at least some structure elements are assigned a position element (OWN; ATR; SRT), determining the context of the structure element. The invention also concerns a corresponding database system.

[0012] File shall here be understood in such manner that it can be stored physically on an arbitary block-addressable data storage, such as a commercially available secondary data storage. Further, several files can be stored in one physical device.

[0013] The invention offers a flexible and effective method for storing and retrieving data, and it offers a number of advantages compared with prior-art methods. Among other things, the invention offers a very compact database with high data density, the memory space being effectively utilized, and, in particlular the invention enables effective data storing and retrieval on a block-addressable storing device. Further the method is universally applicable and the structure elements are independent of data types. Further, with this invention it is simple to define and redefine concepts and concept structures, e.g. “Data Dictionary”. The Data Dictionary can be expanded while an application using it is in operation, whereas the database is totally dynamic and governed by actual needs. Hence, the invention enables defining and developing, among other things, dynamic record types with no need for reorganizing data or modifications of existing software programs using the data. The method according to the invention offers a number of entries for structure element retrieval.

[0014] Further it is preferred to store data in files for text elements and accelerator elements. These additional elements are stored, preferably, as flat tables, i.e. not hierarchically, each in its own file, reflecting portions of the information stored in the hierarchic structure element file. These complementary elements facilitate enhanced data interpretation and faster retrieval and processing.

[0015] Particularly the text elements preferably comprise text associated with data stored in the corresponding structure element(s). As a result, the text elements are well suited for presenting structure element data that requires a textual interpretation. Further, the text file can be used as a retrieval path to the structure element file.

[0016] Particularly the accelerator elements preferably comprise clusters of data from several structure elements, enabling effective data retrieval in the structure element file based on compound conditions represented by the content in two or more structure elements.

[0017] Software using data stored according to the invention can hereby establish a set of concepts and concept values, interpretable by the software. Further, the domain of concepts can be developed with contents and associated procedures within frames determined by the software. This makes it possible to develop general tools for application system development.

[0018] Further advantages and distinctive features of the invention will be seen in the claims and the description of preferred embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The enclosed drawing shows in FIG. 1 a block diagram of the logical relations between the element files according to a preferred embodiment of the invention.

DESCRIPTION OF PREFERRED EMBODIMENTS

[0020] The invention concerns a method for defining, storing, retrieving and interpretation of data, and a corresponding database system, to be built according to the method of the invention.

[0021] A fundamental property of the invention is regarding data as pairs containing a concept and a concept value (Concept;Value). Thus, every structure element becomes a self-contained information carrier. Example: (PERSON;“Adam Smith”) and (AGE; 54). Such structure elements can be connected vertically in Parent/Child-relations, where the Child-element can be interpreted as an attribute of the Parent-element. Thus a hierarchic context-structure is created. Thus, in the example above (PERSON; “Adam Smith”) has the attribute (AGE; 54), that is, (AGE; 54) dwells in the context (PERSON; “Adam Smith”). Hence, a record, as used by conventional database systems, using the invention can be replaced by a concept represented by a structure element, having one or more structure elements connected to it as attributes. The method according to the invention allows such structures of arbitrary vertical depth, and it allows likewise an arbitrary number of different attributes on each vertical level, and it allows an arbitrary number of values of each attribute on each level.

[0022] The Structure Element

[0023] Hence, according to the invention, data is arranged in such self-contained structure elements, which are stored in a structure element file as shown in FIG. 1. A structure element comprises a data element, and this in turn comprises a concept, CPT, and a concept value, INS. Further, the structure element comprises an identification element, SID, being the primary key for the structure elements, enabling unique identification.

[0024] Further a structure element comprises a position element, used for creating and interpreting relations between structure elements. In this way contexts are created. The first part of the position element, OWN, contains information concerning vertical relations between structure elements, and a hierarchy of structure elements can be created. The OWN-property of a structure element contains the SID of its Parent-structure element.

[0025] Further, the position element contains a second part containing information concerning horizontal relations between structure elements, denoting the relations between structure elements on the same hierarchic level. This second part comprises two horizontal position properties, a primary positioning, ATR, that can be interpreted as attribute and a secondary positioning, SRT, that can be interpreted as an attribute-value positioning. The position properties organise the structure elements in the structure element file on each level of the structure element hierarchy.

[0026] The last property, SRT, can preferably be used for validating different values of an attribute using context defined by other structure elements. Such an application of the invention is illustrated in the example below.

[0027] Hence, the structure elements have six (6) properties, which can be divided in three (3) categories: Identification, Position (context) and Data The structure element properties are shown in the table below, where the format preferably can be numeric: Field# Field name Explanation 1 SID Structure element identity 2 OWN Parent-concept SID. Vertical structure 3 ATR Attribute. Primary horizontal position 4 SRT Attribute value sequencing Secondary horizontal position 5 CPT Concept 6 INS Instance (concept content)

[0028] The identification, SID, can preferably be an integer, identifying an occurrence and serving as a primary key for the structure element file. The vertical position property, OWN, contains the primary key to the Parent structure element. This property of the technique creates vertical Parent/Child relations. The first horizontal position property, ATR, can preferably be an integer ordering Child-elements, being used for ordering attributes. The second horizontal position property, SRT, can preferably be an integer ordering Child-elements with the same owner and attribute but with different values (INS) of the concept (CPT) declared for the attribute. This can be used for ordering multiple attribute values, often referred to as “repeating group”.

[0029] The vector {OWN,ATR,SRT,CPT,INS}={0,0,0,n,m} is called a basic occurrence, which is the occurrence on the highest level of a hierarchic structure of concept CPT=n with the contents INS=m. All structure elements, being defined with attributes, text representation or accelerator representation, must have a basic occurrence. This will be described in more detail in the following.

[0030] Retrieval Mechanisms for the Structure File

[0031] There are several possible ways to retrieve individual structure elements in the structure element file as described above. One way, in the following called INDEX 0, is direct retrieval using the identification (SID) in Field# 1. An alternative, in the following called INDEX 1, is applying indirect retrieval via the vector {OWN, ATR, SRT, CPT, INS}, that is Field# 2, 3, 4, 5 and 6. Yet another alternative, in the following called INDEX 2, is applying indirect retrieval using the vector {CPT, INS, ATR, SRT, OWN}, that is Field# 5, 6, 3, 4 and 2.

[0032] The access mechanisms for the elements of the structure element file are limited by the properties of the structure elements as described above. Using the primary key (INDEX 0), it is easy to retrieve a Parent-element of a Child-element. INDEX 1 is an effective mechanism for finding Child-elements in the structure hierarchy. INDEX 2 is suitable for retrieving specific concepts and concept values traversing the structure hierarchy.

[0033] Further, the method according to the invention comprises two additional elements, completing the method. These elements will be described in more detail in the following.

[0034] Depending on the quantity of data and its character, the properties of the structure element may prove insufficient. In this case the TEXT ELEMENT or the ACCELERATOR ELEMENT, described below, can be used.

[0035] The Text Element

[0036] Data in the structure element file, best being represented by text, can conveniently be completed with text element(s) in the text element file. A text element is related to a basic occurrence in the structure element file, as described above and as shown in FIG. 1.

[0037] The only purpose of the text element is transforming the numeric representation of data in the structure element into a text representation. The text element, according to the invention is used to retrieve, order and present data in an alphanumeric format.

[0038] The access mechanisms of the text element should be programmed in such a way that text elements are stored and retrieved statically or dynamically. Static implies that references to text elements are predefined in the software. Dynamic implies that programs using the method according to the invention can accept instructions as to how to use text elements.

[0039] It should be noted that, to use text structurally, texts must be categorised with reference to concept definitions and be represented, preferably numerically, in the structure element file. This indicates that text element strictly is a mechanism for presentation and access.

[0040] For identification purposes, the text elements preferably comprise properties corresponding to those in the structure element. These properties are CPT and INS, identifying a basic occurrence in the structure file. The text element also preferably comprises a property to ensure uniqueness (UNQ) in the case where more than one basic occurrence in the structure file have the same text representation. The text elements also comprise a text property, holding the text representation (TXT). Other properties of the text element are an index (IDX) preferably used for defining several text representations to one structure element, and a property used for defining several text alternatives to a certain text representation (ALT).

[0041] The properties of the text elements, preferred terms and field sequence are presented in the following table, where the formats preferably can be numeric and alphanumeric: Field# Fieldname Explanation 1 CPT Concept 2 INS Concept instance number 3 IDX Text representation definition 4 ALT Alternative text representations 5 UNQ Optional for element uniqueness 6 TXT Text representation

[0042] Access Mechanisms for Text Elements

[0043] There are several ways to retrieve individual text elements of the text element file, as described above. One way, in the following called INDEX 1, is applying indirect retrieval using the vector {CPT, INS, IDX, ALT}, that is Field# 1, 2, 3 and 4. Another way, in the following called INDEX 2, is applying indirect retrieval using the vector {CPT, IDX, TXT, UNQ}, that is Field# 1, 3, 6 and 5.

[0044] The access mechanisms of the text file have the following purposes: INDEX 1 connects a basic occurrence in the structure element file with one or more text representations, whilst INDEX 2 is used for retrieving a basic occurrence in the structure element file using a text representation.

[0045] The Accelerator Element

[0046] To increase retrieval effectivity in the structure element file, the method according to the invention further comprises an accelerator element, referring to a number of attributes (direct context via the relation) or other structure elements (indirect context, preferably defined in the application). Together, the attribute references identify a basic occurrence in the structure element file. The accelerator elements are stored in an accelerator element file as shown in FIG. 1. The objective of the accelerator element is enabling a basic occurrence in the structure element file using references to data in several structure elements simultaneously. Using several structure elements, compound retrieval sets can be constructed. This reduces structure element retrieval time considerably.

[0047] In the same way as the text element, the access mechanisms of the accelerator element are to be programmed in such a way that accelerator elements are stored and retrieved statically or dynamically. Static implies that references to accelerator elements are predefined in the software. Dynamic implies that programs using the method according to the invention can accept instructions as to how to use the accelerator elements.

[0048] To enable structure element identification, the accelerator element preferably comprises some properties common to the structure element. These are CPT and INS identifying a basic occurrence in the structure element file. The accelerator element also comprises a property to ensure uniqueness (UNQ) in the case several basic occurences can have the same attribute reference representation.

[0049] Other properties of the accelerator element are an index, IDX, preferably used to define several reference representations for a basic occurrence, and a property, ALT, preferably used to enable several alternative reference representations for a specific index to a basic occurrence. Finally the accelerator element contains an arbitrary number of properties, REF1-REFn, containing the references.

[0050] The properties of the accelerator element, preferred terms and field sequence are presented in the following table, where the format preferably can be numeric: Field# Fieldname Explanation 1 CPT Concept 2 INS Instance 3 IDX Reference representation 4 ALT Alternative reference representations 5 UNQ Optional, to create uniqueness 6 REF1 Reference #1 7 REF2 Reference #2 . . . . . . . . . n + 5 REFn Reference #n

[0051] Access Mechanisms for the Accelerator Element

[0052] There are several ways to retrieve individual elements in the accelerator element file as described above. One way, in the following called INDEX 1, is applying indirect retrieval using the vector {CPT, INS, IDX, ALT}, that is Field# 1, 2, 3 and 4. Another way, in the following called INDEX 2, is applying indirect retrieval using the vector {CPT, IDX, REF1, . . . , REFn, UNQ}, that is Field# 1, 3, 6, . . . , n+5 and 5.

[0053] The access mechanisms of the accelerator element have the following purpose: INDEX 1 connects a basic occurrence in the structure element file with one or more reference representations, while INDEX 2 is used for retrieving a basic occurrence in the structure file using a set of references.

[0054] An Example of Storing Data Using the Invention

[0055] In the following an illustration of the storing method according to the invention is presented. The illustration was brought from an application being a platform for modelling business operations, that is a set of utilities used to implement tailor-made systems for administering business. The modelling is completely based on data.

[0056] Some predefined concepts used in the example are:

[0057] Constructor. A super-concept, from which all other concepts are created. That is, all other concepts are concept values (instances) of the super-concept, Constructor. All concepts have a number of predefined properties; e.g Data type, Data format, Redefine and a Bitmap property, holding, among other things, a bit denoting multiple attribute representation (repeating group). Constructor's Data type is Text. Hence all concepts (instances of Constructor) are presented with text.

[0058] Redefine. A concept with the property Redefine is a redefinition of another concept, that is, it shares its properties and value domain.

[0059] Data type. All concepts have a data type There are two categories of data types: scalar and structure. “Numeric”, “Date”, “Date&Time” and “Boolean” are scalar. All scalar data are stored in fixed point numeric format. “Text”, “Configuration” and “Record” are structures. Contents in scalar concepts are identified and interpreted by their instance numbers data format.

[0060] When assigning an attribute to a concept the understanding of the concept will increase from the point of view of content. The content of a structure-category concept is identified by its instance number, but it is interpreted differently. Text is interpreted through representation in the text element file. Configuration is interpreted through a subset of or all of its attributes, having the property “premise”. Record is interpreted in an attribute context. Record is not represented in the example.

[0061] Data format. Scalar data format denotes the total number of integer and decimal digits in fixed point notation. This is illustrated only with the concept thickness (see below −0.5 mm is stored as 5). Instances of structure data have fixed format=8 digits. Text data is formatted with the maximum number of characters.

[0062] Function. Instances of Function are arithmetic or logic functions. The algorithm is described structurally using attributes. This is not illustrated in the example.

[0063] Premise. An attribute, being part of the identification set of attributes should have property Premise. Premise attributes are enumerated from 1 to n.

[0064] Concepts used in the example are; Pressed plate, a user defined thin, form-cut and pattern pressed sheet of metal. Its Data type=“Configuration”. A Pressed plate is interpreted through its attributes: Plate type, Metal and Thickness. Plate type is user-defined with attributes Length, Width, Plate class and Standard thickness. The Standard thickness of a Pressed plate depends on Plate class and the Metal-value. A Metal has a Specific weight.

[0065] The application has a rather simple storing structure: Level 0 Level 1 Level 2 — — — Concept -----> Attribute -----> Property -----> Property

[0066] Concept is the highest level and can have one or more Attributes and/or one or more Properties. An Attribute can have one or more Properties. Attributes and Properties are references to Concepts. A Property imposes limitations on its Concept or Attribute (e.g. data type, the validity of a value . . . ).

[0067] To use the method according to the invention in a general manner, conventions for interpretation of predefined concepts and their values need to be clarified:

[0068] Concept: A numeric representation of a concept definition. In this data dictionary, a super-concept with text representation “Constructor” is defined. This super-concept is the basis for defining all other concepts. The super-concept, Constructor, has numeric representation 1 (one).

[0069] Instance: A numeric representation of contents associated with a Concept. Together Concept and Instance create a pair (Concept, Instance) being a self-contained information carrier in program systems using the method according to the invention. Examples: (1,10) and (10,5). The interpretation of these pairs could be (1,10)=(Constructor,“Name”) and (10,5) =(Name, “Adam”).

[0070] In this data dictionary the interpretation of (Concept, Instance) is as follows:

[0071] If Concept=1, that is the interpretation of Concept=“Constructor”, the pair is interpreted as a concept definition. If Concept>1 the pair is interpreted as concept content. Concept must be >0.

[0072] BasicData is a basic occurrence of a pair (Concept,Instance). In a structure element the BasicData is described using the vector:

[0073] {OWN,ATR,SRT,CPT,INS}={0,0,0,Cpt,Ins} where Cpt>0, and is assigned a unique SID (structure element identifier). BasicData is level 0 in the element structure.

[0074] Attribute widens the contents of a basic occurrence. The Attribute structure element is described with the vector:

[0075] {OWN,ATR,SRT,CPT,INS}={Own,Atr,Srt,RefCpt,RefIns} where Own>0, Atr>0, Srt>=0 and the pair (RefCpt,RefIns) can identify a basic occurrence (0,0,0,RefCpt,RefIns).

[0076] Attribute is level 1 in the element structure.

[0077] Property interprets and limits the validity of a basic occurrence or an attribute. Property is described in a structure element using the vector:

[0078] {OWN,ATR,SRT,CPT,INS}={Own,0,0,PrpCpt,PrpIns} where OWN>0 and the pair(PrpCpt,PrpIns) point at the basic occurrence of (0,0,0,PrpCpt,PrpIns).

[0079] Property is level 1 or 2 for the structure element. There are two categories of properties:

[0080] Concept specific properties, being assigned contents when defining a concept, and instance specific properties, being assigned contents when assigning contents to the concept.

[0081] The application has about 50 predefined concepts. Other concepts are added when modelling the application (i.e. implementing the system).

[0082] The notation below complies with the formal description above. In this example the Data Dictionary structure elements for concept definitions are as follows: SID OWN ATR SRT CPT INS Explanation 1 0 0 0 1 1 Concept = Constructor: (Super-concept No.1) 2 0 0 0 1 2 Concept = Redefine: (Concept Redefinition - No.2) 3 2 0 0 2 1 Concept = Redefine PRP: Redefine = Concept 4 0 0 0 1 8 Concept = Data type - No.8 5 0 0 0 8 1 Data type = Text 6 0 0 0 8 2 Data type = Numeric 7 0 0 0 8 3 Data type = Configuration 8 4 0 0 8 1 Concept = Data type PRP: Data type = Text 9 1 0 0 8 1 Concept = Concept PRP: Data type = Text 10 0 0 0 1 9 Concept = Format - No.9 11 0 0 0 1 19 Concept = Function - No.19 12 11 0 0 8 1 Concept = Function PRP: Data type = Text 13 0 0 0 1 10 Concept = Bitmap - No.10 14 0 0 0 1 30 Concept = Premise - No.30 Concepts defined when modelling: 20 0 0 0 1 301 Concept = SpecificWeight No301 21 20 0 0 8 2 Concept = SpecificWeight PRP: Data type = Numeric 22 0 0 0 1 202 Concept = Metal - No.202 23 22 0 0 8 1 Concept = Metal PRP: Data type = Text 24 22 1 0 1 301 Concept = Metal ATR 1: Concept = SpecificWgt 25 0 0 0 1 203 Concept = Thickness 26 25 0 0 8 2 Concept = Thickness PRP: Data type = Numeric 27 25 0 0 9 21 Concept = Thickness PRP: Data format = 21 (ie 99.9) 28 0 0 0 1 302 Concept = StdThickness 29 28 0 0 2 203 Concept = StdThickness PRP: Redefine = Thickness 30 0 0 0 1 303 Concept = Width 31 30 0 0 8 2 Concept = Width PRP: Data type = Numeric 32 0 0 0 1 304 Concept = Length 33 32 0 0 8 2 Concept = Length PRP: Data type = Numeric 34 0 0 0 1 305 Concept = Plate class 35 0 0 0 1 201 Concept = Plate type 36 35 0 0 8 1 Concept = Plate type PRP: Data type = Text 37 35 1 0 1 302 Concept = Plate type ATR 1: Concept = StdThickn. 38 37 0 0 1 19 Concept = Plate type ATR 1: PRP: Concept = Function 39 37 0 0 10 8 Concept = Plate type ATR1: PRP: BitMap = 8 (Mult atr) 40 35 2 0 1 303 Concept = Plate type ATR 2: Concept = Width 41 35 3 0 1 304 Concept = Plate type ATR 3: Concept = Length 42 35 4 0 1 305 Concept = Plate type ATR 4: Concept = Plate class 43 0 0 0 1 101 Concept = PressedPlate 44 43 0 0 8 3 Concept = PressedPlate PRP: Data type = Configuration 45 43 1 0 1 201 Concept = PressedPlate ATR 1: Concept = Plate type 46 45 0 0 30 1 Concept = PressedPlate ATR 1: PRP: Premise = 1 47 43 2 0 1 202 Concept = PressedPlate ATR 2: Concept = Metal 48 47 0 0 30 2 Concept = PressedPlate ATR 2: PRP: Premise = 2 49 48 3 0 1 203 Concept = PressedPlate ATR 3: Concept = Thickness 50 49 0 0 30 3 Concept = PressedPlate ATR 3: PRP: Premise = 3

[0083] The corresponding elements in the text element file, according to the invention, for the basic occurrences in the structure elements of the Data Dictionary above will be as shown in the table below: CPT INS IDX ALT UNQ TXT 1 1 0 0 0 Concept 1 8 0 0 0 Data type 8 1 0 0 0 Text 8 2 0 0 0 Numeric 8 3 0 0 0 Configuration 1 9 0 0 0 Data Format 1 19 0 0 0 Function 1 30 0 0 0 Premise Defined when modelling: 1 301 0 0 0 Specific Weight 1 202 0 0 0 Metal 1 203 0 0 0 Thickness 1 302 0 0 0 Std Thickness 1 303 0 0 0 Width 1 304 0 0 0 Length 1 305 0 0 0 Plate class 1 201 0 0 0 Plate type 1 101 0 0 0 Pressed Plate

[0084] Examples of elements of data in the structure element file, according to the invention, using the Data Dictionary as shown above are shown in the table below: SID OWN ATR SRT CPT INS Comment 101 0 0 0 301 4 Specific weight = 4 kg/dm3 102 0 0 0 301 8 Specific weight = 8 kg/km3 103 0 0 0 202 1 Metal = Stainless 104 103 1 0 301 8 Metal = Stainless ATR 1: Specific weight = 8 105 0 0 0 202 2 Metal = Titanium 106 105 1 0 301 4 Metal = Titanium ATR 1: SpecificWeight = 4 107 0 0 0 203 5 Thickness = 0.5 mm. 108 0 0 0 203 6 Thickness = 0.6 mm 109 0 0 0 303 385 Width = 385 mm 110 0 0 0 303 505 Width = 505 mm 111 0 0 0 304 940 Length = 940 mm 112 0 0 0 304 1348 Length = 1348 mm 113 0 0 0 19 1 Function = StdGX-05 114 0 0 0 19 2 Function = StdGX-06 115 0 0 0 305 1 Plate class = GX 116 0 0 0 201 1 Plate type = GX-26 117 116 1 1 302 5 Plate type = GX-26 ATR1: SRT1: StdThickn = 0.5 mm 118 117 0 0 19 1 Platetype = GX-26 ATR1: SRT 1: PRP Function = StdGX-05 119 116 1 2 302 6 Plate type = GX-26 ATR1: SRT2: StdThickn = 0.6 mm 120 119 0 0 19 2 Plate type = GX-26 ATR1: SRT 2: PRP: Function = StdGX-06 121 116 2 0 303 385 Plate type = GX-26 ATR 2: Width = 385.mm 122 116 3 0 304 940 Plate type = GX-26 ATR 3: Length = 940 mm 123 123 4 0 305 1 Plate type = GX-26 ATR 4: Plate class = GX 124 0 0 0 201 2 Plate type = GX-42 125 124 1 1 302 5 Plate type = GX-42 ATR1: SRT1: StdThickn = 0.5 mm 126 125 0 0 19 1 Plate type = GX-42 ATR 1: SRT 1: PRP: Function = StdGX-05 127 124 1 2 302 6 Plate type = GX-42 ATR1: SRT2: StdThickn = 0.6 mm 128 127 0 0 19 2 Plate type = GX-42 ATR 1: SRT 2: PRP: Function = StdGX-06 129 124 2 0 303 385 Plate type = GX-42 ATR 2: Width = 385 mm 130 124 3 0 304 1348 Plate type = GX-42 ATR 3: Length = 1348 mm 131 124 4 0 305 1 Plate type = GX-42 ATR 4: Plate class = GX 132 0 0 0 101 1 PressedPlate = 1 (GX-26, Stainless, 0.5 mm) 133 132 1 0 201 1 PressedPlate = 1 ATR 1: Plate type = GX-26 135 132 2 0 202 1 PressedPlate = 1 ATR 2: Metal = Stainless 137 132 3 0 203 5 PressedPlate = 1 ATP 3: Thickness = 0.5 mm 139 0 0 0 101 2 PressedPlate = 2 (GX-42, Stainless, 0.5 mm) 140 139 1 0 201 2 PressedPlate = 2 ATR 1: Plate type = GX-42 142 139 2 0 202 1 PressedPlate = 2 ATR 2: Metal = Stainless 143 139 3 0 203 5 PressedPlate = 2 ATR 3: Thickness = 0.5 mm

[0085] The corresponding elements in the text element file, according to the invention, of basic occurrences in the structure elements as above will be as shown in the following table: CPT INS IDX ALT UNQ TXT 202 1 0 0 0 Stainless 202 2 0 0 0 Titanium 19 1 0 0 0 StdGX-05 19 2 0 0 0 StdGX-06 201 1 0 0 0 GX-26 201 2 0 0 0 GX-42 305 1 0 0 0 GX

[0086] The corresponding elements in the accelerator file, according to the invention, of basic occurrences in the structure elements as above will be as shown in the following table: REF REF CPT INS IDX ALT UNQ 1 REF 2 3 TXT 101 1 30 0 0 1 1 5 PressedPlate GX-26, Stainless, 0.5 mm 101 2 30 0 0 2 1 5 PressedPlate GX-42, Stainless, 0.5 mm

[0087] This application of the accelerator elements has the objective of fast retrieval of basic occurrences using the Premises (IDX=30). The index becomes unique without using UNQ, whereas UNQ=0.

[0088] Find below a logical presentation of portions of the database above concerning Pressed plate GX-42 (column header SID Nos 139-143, 113-114, 115, 124-131, 103-112 and 101-102): Concept -> Attribute -> Property (PressedPlate, 2) -> (Platetyp, “GX-42”) -> (Metal, “Stainless”) -> (Thickness, 0.5) (Platetype, “GX-42”) -> (StdThickn, 0.5) -> (Function, “StdGX-05”) -> (StdThickn, 0.6) -> (Function, “StdGX-06”) -> (Width, 385) -> (Length, 1348) -> (Plate class, “GX”) (Function, “StdGX-05”) -> Not specified in the example (Function, “StdGX-06”) -> Not specified in the example (Plate class, “GX”) (Metal, “Stainless”) -> (SpecificWeight, 8) (Metal, “Titanium”) -> (SpecificWeight, 4) (Thickness, 0.5) (Thickness, 0.6) (Width, 385) (Width, 505) (Length, 940) (Length, 1348) (SpecificWeight, 4) (SpecificWeight, 8)

[0089] Instances of Pressed plate are interpreted via the contents of the premise attributes of Pressed plate, that is, the contents of Plate type, Metal and Thickness. Instances of Plate type and Metal are interpreted via their text elements. Instances of Thickness are interpreted via the Data format of Thickness. (Function, “StdGX-05”) is part of the domain of rules. It governs the selection of plate thickness. Example: (Function,“StdGx-05”)−({Metal} EQUAL “Stainless”) (Function,“StdGX-06”)−({Metal} NOT EQUAL “Stainless”). The notation {Metal} is interpreted as “the content of the concept Metal in the current context”. The quantity Metal in a Pressed plate, can be calculated by a numeric (Function,“Plate weight”): {Specificweight}*{Thickn}*{width}*{Length}.

[0090] Example of a Physical Implementation of the Method.

[0091] In the example above the three elements, according to the method of the invention, are implemented in a file system labelled “Index Sequential Access Method” (ISAM). The implementation uses only a small part of the facilities of the file system. Generally, the requirements of the technique are that the file system can store and sort alphanumeric and numeric data. In addition the file system needs to allow two index files connected with each data file, and each index containing up to 16 data fields. Below follows an example how the storing preferably can be accomplished.

[0092] The structure elements are stored in three physical files; a data file, STRUCTUR.DAT, and two associated index files, STRUCTUR.IX1 and STRUCTUR.IX2, together constituting the structure element file. The data file sorts the elements by the property SID, being a number identifying an element uniquely. This order of elements is denoted INDEX 0 for the structure elements. In this file system SID is a number indicating the position of the element (the record) in the data file, and is not stored as part of the element.

[0093] The two index files contain INDEX 1 and INDEX 2 as defined for the structure element. The index files are maintained automatically by the file system. In this file system, numeric data is stored in BCD-format (Binary Coded Decimal), and alphanumeric data in ASCII-format.

[0094] The structure file can preferably be dimensioned for 99,999,999 structure elements. The formats of the properties of the structure element file are:

[0095] STRUCTUR/SID: Integer (NumeriC identification not being stored)

[0096] STRUCTUR/OWN: 8 BCD-digits (4 bytes)

[0097] STRUCTUR/ATR: 2 BCD-digits (1 byte)

[0098] STRUCTUR/ALT: 6 BCD-digits (3 bytes)

[0099] STRUCTUR/CPT: 4 BCD-digits (2 bytes)

[0100] STRUCTUR/INS:12 BCD-digits (6 bytes)

[0101] BCD is the storing format of the structure element properties. However, any sortable numeric format can be used. The field sizes of the properties are governed by the requirements of the application. Essential for choosing format and field sizes is minimising the secondary storage space used by each structure element. It should be adjusted to the block size of the storage device.

[0102] As all properties are defined as integers, the application using the structure element needs to interpret the numeric contents to other scalar types (Date, ASCII, Boolean, Numeric etc). The interpretation is governed by a “Data Dictionary”, itself stored as structure elements.

[0103] The text elements are stored in three physical files; one data file, TEXT.DAT, and two associated index files, TEXT.IX1 and TEXT.IX2, together constituting the text element file.

[0104] The two index files contain INDEX 1 and INDEX 2 as defined for the text element. The index files are maintained automatically by the file system.

[0105] The text file can preferably be dimensioned for 1,000,000 elements. The formats of the properties of the text element are:

[0106] TEXT/CPT: 4 BCD-digits (2 bytes)

[0107] TEXT/INS:12 BCD-digits (6 bytes)

[0108] TEXT/IDX: 2 BCD-digits (1 byte)

[0109] TEXT/ALT: 2 BCD-digits (1 byte)

[0110] TEXT/UNQ: 8 BCD-digits (4 bytes)

[0111] TEXT.TXT:50 ASCII-characters (50 bytes)

[0112] The size of the text field is a compromise considering the size requirements of the text representations and minimising the space requirements of the text elements. The block size used by this file system is a multiple of 64 bytes. The definitions also need to consider index limitations of the file system.

[0113] The accelerator elements are stored in three physical files; a data file, ACCEL.DAT, and two associated index files, ACCEL.IX1 and ACCEL.IX2, together constituting the accelerator element file. The two index files contain INDEX 1 and INDEX 2 as defined for the accelerator element. The index files are maintained automatically by the file system.

[0114] The accelerator file is preferably dimensioned for 1,000,000 elements. The format of the properties of the accelerator element are:

[0115] ACCEL/CPT: 4 BCD-digits (2 bytes)

[0116] ACCEL/INS:12 BCD-digits (6 bytes)

[0117] ACCEL/IDX: 2 BCD-digits (1 byte)

[0118] ACCEL/ALT: 2 BCD-digits (1 byte)

[0119] ACCEL/UNQ: 8 BCD-digits (4 bytes)

[0120] ACCEL/REF01: 8 BCD-digits (4 bytes)

[0121] ACCEL/REF02: 8 BCD-digits (4 bytes)

[0122] ACCEL/REF03: 8 BCD-digits (4 bytes)

[0123] ACCEL/REF04: 8 BCD-digits (4 bytes)

[0124] ACCEL/REFOS: 8 BCD-digits (4 bytes)

[0125] ACCEL/REF06: 8 BCD-digits (4 bytes)

[0126] ACCEL/REF07: 8 BCD-digits (4 bytes)

[0127] ACCEL/REF08: 8 BCD-digits (4 bytes)

[0128] ACCEL/REF09: 8 BCD-digits (4 bytes)

[0129] ACCEL/REF10: 8 BCD-digits (4 bytes)

[0130] ACCEL/REF11: 8 BCD-digits (4 bytes)

[0131] ACCEL/REF12: 8 BCD-digits (4 bytes)

[0132] The number of reference fields in the element limits the number of properties that can be used in a compound retrieval. In the example above, the accelerator element corresponds to an index definition with up to 12 properties. The application using the file definition uses maximum 11 of the references.

[0133] Specialized Physical Implementation of the Method

[0134] The elements have a fixed logical structure. However, they are flexible considering format and field property dimensioning. Defining element files requires only a small number of parameters influencing needs for secondary storage space and effectivity of the file system.

[0135] As the structural connection between element properties is predefined, general methods for maintenance and retrieval of data in the physical files can be specified.

[0136] Specifying a file system suiting the elements and an interface defined by standard methods for maintenance and retrieval of data in the element files together with a cache-system optimising the use of secondary and primary storage, considerable effectivity improvements can be achieved. If such a file system is adjusted to and included in an operating system, additional effectivity improvements can be achieved.

[0137] The elements can store any type of data. One advantage of selecting a standardised method for storing all types of data is that a combination of customised electronic devices and standardised software in several layers can create a common platform for all types of storing and retrieval needs.

SUMMARY OF THE INVENTION

[0138] The method according to the invention is universally applicable. Hence, it enables storing any type or structure of data. The method is based on the fact that structure elements are self-contained carriers of information, represented by a pair: concept and concept value, and context information adherent to it.

[0139] According to the invention, data can be organised in hierarchies of structure elements of arbitrary depth and complexity. In spite of its simplicity, the method can reflect connection, context and meaning, however complex, irrespective of types of data and how complex the relations between data may be. Hence, the method represents a fundamental framework for standardised physical data storage of all types of data.

[0140] The method according to the invention can be implemented in virtually any reasonably advanced ISAM-file system, or another suitable commercially available file system, or a file system developed and dedicated to this purpose.

[0141] The invention has now been described above with a preferred embodiment. However, it is obvious that many variations of it can be implemented. As an example, it is possible to employ more, other and even fewer fields in the structure element, the text element and/or the accelerator element. It is also possible to use only the structure element, and not use the text element or the accelerator element. Further, it is possible to define different fields, as for example the identification, differently from what has been described above. Such and other kindred variations must be seen as comprised by the invention as defined by the appended claims. 

1. A method for storing data, in which data is organised in structure elements which are stored in a structure file and comprise two properties (CPT, INS) intended to be interpreted as concept (CPT) and concept value (INS), characeterised in that the structure element further is assigned an identification property (SID) enabling unique identification of a structure element, and at least one, and, preferably, at least three position properties (OWN, ATR, SRT), defining a structure element's relations to other structure elements.
 2. A method according to claim 1, wherein the position property (OWN) governs the vertical relations between structure elements, hereby creating hierarchic relations between structure elements.
 3. A method according to claim 1, wherein the position property (OWN) concerning the vertical relationship of a structure element is assigned the value of the identification property (SID) of a structure element on a higher hierarchical level, with which said structure element is connected, in case such a structure element exists.
 4. A method according to claim 2 or 3, wherein the position properties (ATR) and (SRT) of the structure element further govern the ordering of the structure elements in hierarchic relations.
 5. A method according to claim 4, wherein the position properties governing the ordering of the structure elements in hierarchic relations comprise a property (ATR) governing primary order between the structure elements.
 6. A method according to claim 5, wherein the position properties concerning ordering of the structure elements in hierarchic relations comprise a property (SRT) governing secondary order between structure elements, conditioned by a certain primary order (ATR).
 7. A method according to any one of the preceding claims, wherein at least some of the structure elements in a hierarchic relation further can be subjected to a condition, to be fulfilled for a hierarchic relation to be valid.
 8. A method according to claim 7, wherein a position property (SRT) is adapted to be interpreted as an attribute value ordering, allowing several different values of one attribute (ATR) to be valid depending on a certain contextual situation.
 9. A method according to any one of the preceding claims, wherein all structure elements are assigned an identification property (SID), a position property (OWN) concerning hierarchic relations between structure elements, which preferably is assigned the value of the identification property (SID) of a structure element on a higher hierarchic level, a position property (ATR) defining the primary order among structure elements in a hierarchic relationship, a position property (SRT) defining the secondary order among structure elements conditioned by the position property (ATR) in a hierarchic relationship, and a concept (CPT) and a concept value (INS).
 10. A method according to any one of the preceding claims, comprising the further step, for at least some of the elements in the structure element file, of storing, in a text element file, the properties (CPT, INS), identifying a basic occurrence of the structure element file, together with a text property (TXT) containing a text representation of at least a part of the information in the corresponding basic occurrence in the structure element file.
 11. A method according to claim 10, wherein the text elements further comprise a property (UNQ) distinguishing several text elements and preferably containing 0 (zero) or the itentifying property (SID) of the corresponding basic occurrence.
 12. A method according to claims10 or 11, wherein the text elements further comprise an interpretation property (IDX) defining how to interpret a text representation, and preferably also an interpretation alternative property (ALT) defining alternative text representations of an interpretation (IDX).
 13. A method according to any one of claims 10-12, wherein the rules concerning selection of structure elements to have text representation are predefined in the software using the elements.
 14. A method according to any one of claims 10-12, wherein the rules concerning selection of structure elements to have text representation are defined dynamically supported by the software using the elements.
 15. A method according to any one of the preceding claims, comprising the further step, for at least some of the elements in the structure element file, of storing, in an accelerator element file, the properties (CPT, INS), identifying a basic occurrence of the structure element file, together with at least one reference property (REF1, REF2, . . . , REFn), intended to contain some data from the structure element hierarchy of said basic occurrence.
 16. A method according to claim 15, wherein the accelerator element further comprises a distinguishing property (UNQ), preferably containing 0 (zero) or the identifying property (SID) of the corresponding basic occurrence in the structure element file.
 17. A method according to claim 15 or 16, wherein the accelerator element further comprises an interpretation property (IDX), defining how to interpret the accelerator representation, and preferably also an interpretation alternative property (ALT), providing for alternative accelerator representations for a certain interpretation (IDX).
 18. A method according any one of claims 15-17, wherein the rules concerning selection of structure elements to have data stored as references in the accelerator element file are predefined in the software using the elements.
 19. A method according to any one of claims 15-17, wherein the rules concerning selection of structure elements to have data stored as references in the accelerator element file are defined dynamically supported by the software using the elements.
 20. A database system comprising a structure element file, where data is organised in structure elements, stored in a structure file, the structure elements comprising two properties (CPT, INS) intended to be interpreted as concept (CPT) and concept value (INS) characterised in that the structure element further is assigned an identification property (SID) enabling unique identification of a structure element, and at least one and preferably at least three position properties (OWN, ATR, SRT), defining a structure element's relations to other structure elements.
 21. A database system according to claim 20, wherein the position property (OWN) governs the vertical relations between structure elements, hereby creating hierarchic relations between structure elements.
 22. A database system according to claim 20, wherein the position property (OWN) concerning the vertical relationship of a structure element is assigned the value of the identification property (SID) of a structure element on a higher hierarchical level, with which said structure element is connected, in case such a structure element exists.
 23. A database system according to claim 21 or 22, wherein the position properties (ATR) and (SRT) of the structure element further govern the ordering of the structure elements in hierarchic relations.
 24. A database system according to claim 23, wherein the position properties governing the ordering of the structure elements in hierarchic relations comprise a property (ATR) governing primary order between the structure elements.
 25. A database system according to claim 24, wherein the position properties concerning ordering of the structure elements in hierarchic relations, comprise a property (SRT) governing secondary order between structure elements, conditioned by a certain primary order (ATR).
 26. A database system according to any one of claims 20-25, wherein at least some of the structure elements in a hierarchic relation further can be subjected to a condition, to be fulfilled for a hierarchic relation to be valid.
 27. A database system according to claim 26, when this is depending on claim 25, wherein a position property (SRT) is adapted to be interpreted as an attribute value ordering, allowing several different values of one attribute (ATR) to be valid depending on a certain contextual situation.
 28. A database system according to any one of claims 20-27, wherein all structure elements are assigned an identification property (SID), a position property (OWN) concerning hierarchic relations between structure elements, which preferably is assigned the value of the identification property (SID) of a structure element on a higher hierarchic level, a position property (ATR) defining the primary order among structure elements in a hierarchic relationship, a position property (SRT) defining the secondary order among structure elements conditioned by the position property (ATR) in a hierarchic relationship, and a concept (CPT) and a concept value (INS).
 29. A database system according to any one of claims 20-28, further comprising the step, for at least some of the elements in the structure element file, of storing, in a text element file,the properties (CPT, INS), identifying a basic occurrence of the structure element file, together with a text property (TXT) containing a text representation of at least a part of the information in the corresponding basic occurrence in the structure element file.
 30. A database system according to claim 29, wherein the text elements further comprise a property (UNQ) distinguishing several text elements, the property preferably containing 0 (zero) or the identifying property (SID) of the corresponding basic occurrence.
 31. A database system according to claim 29 or 30, wherein the text elements further comprise an interpretation property (IDX) defining how to interpret a text representation, and preferably also an interpretation alternative property (ALT) defining alternative text representations of an interpretation (IDX).
 32. A database system according to any one of claims 29-31, wherein the rules concerning selection of structure elements to have text representation are predefined in the software using the elements.
 33. A database system according to any one of claims 29-31, wherein the rules concerning selection of structure elements to have text representation are defined dynamically supported by the software using the elements.
 34. A database system according to any one of claims 20-33, further comprising the step, for at least some of the elements in the structure element file, of storing, in an accelerator element file, the properties (CPT, INS), identifying a basic occurrence of the structure element file, together with at least one reference property (REF1, REF2, . . . , REFn), intended to contain some data from the structure element hierarchy of the said basic occurrence.
 35. A database system according to claim 34, wherein the accelerator element further comprises a distinguishing property (UNQ), preferably containing 0 (zero) or the identifying property (SID) of the corresponding basic occurrence in the structure element file.
 36. A database system according to claim 34 or 35, wherein the accelerator element further comprises an interpretation property (IDX), defining how to interpret the accelerator representation, and preferably also an interpretation alternative property (ALT), providing for alternative accelerator representations for a certain interpretation (IDX).
 37. A database system according any one of claims 34-36, wherein the rules concerning selection of structure elements to have data stored as references in the accelerator element file are predefined in the software using the elements.
 38. A database system according to any one of claims 34-36, wherein the rules concerning selection of structure elements to have data stored as references in the accelerator element file are defined dynamically supported by the software using the elements. 